home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 19
/
Night Owl (The Best of Shareware)(NOPV 19)(1996).ISO
/
018a
/
elrul512.zip
/
PBLCKYS.RUL
< prev
next >
Wrap
Text File
|
1995-05-31
|
5KB
|
123 lines
--- Following message extracted from PUBLIC_KEYS @ 1:374/14 ---
By Christopher Baker on Mon May 01 00:52:02 1995
From: Christopher Baker
To: All
Date: 01 May 95 00:51:55
Subj: PUBLIC_KEYS Echo Guidelines - regular repost
-----BEGIN PGP SIGNED MESSAGE-----
This is the PUBLIC_KEYS Echo. The purpose of the Echo is to provide a place
to discuss public-keys for data privacy within FidoNet and elsewhere.
We also consider electronic signature possibilities using public-keys
and discuss data and software encryption and the various schemes and
programs that produce them.
This is a technical Echo with very few rules. Those very few rules are:
1. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.
2. No politics [except as it relates to privacy issues] and no religion.
3. No personal attacks, slurs or innuendo. Stick to issues not
personalities.
4. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is on-topic.
Don't send person-specific encrypted traffic. Such specific traffic
belongs in direct Netmail. Encrypted traffic should be in the form of
ASCII-armored or personal key encrypted messages that can be read by
anyone with PGP 2.6+ and your public-key. Include your public-key in
a separate message before sending such test messages in case the
other end doesn't have it or make them aware of how to get it from
your system. If you just want to post your public-key, use PKEY_DROP
Echo.
5. Clear-signed messages are not encrypted and may be used freely in
this Echo.
6. This Echo may be traveling around the world so try to be concise. Avoid
excessive quoting for one-liner responses.
7. Be aware that Echomail is NOT secure. Don't take anything at face value.
8. The posts in this Echo are the sole responsiblity of the poster. If you
need verification, use Netmail.
9. The Moderators will deal with off-topic traffic. Don't respond for them.
Links to this Echo will only be curtailed when absolutely necessary so
please don't make it necessary. [grin]
The Moderators are Christopher Baker [KeyID: 1024/F89A24F9 1994/05/18]
and GK Pace [KeyID: 1024/EE38FB41 1994/05/14] at 1:374/14 and 1:374/26,
respectively.
It is Gated into Zone 2 by Jens Mueller at 2:24/24 who sends it on to
Harry Bush at 2:51/2. Consult Jens or Harry for Zone 2 feeds. The Echo
is gated into Zone 3 by Jackson Harding at 3:800/857. [thanks, guys!]
The other Zones are open [hint, hint].
It is recommended that individual, public-keys be made available via Netmail
or by file-request with the magic filename: PGPKEY and that the public-key
provided for that request by given a distinctive filename using part or all
of each provider's name and address. For example, on my system, a
file-request of PGPKEY will give BAK37414.ASC to the requesting system. A
magic filename of KEYRING will yield extracts from my Public Keyring as
BAKPUB14.ASC. This will avoid duplicate overwriting and make it easier to
track the keys. Using standard magic filenames will make it easier to find
keys and keyrings on different systems.
The PGP and Privacy and encryption related files on each system should be
maintained with a magic filename for file request. PGPFILES should be set
on all participating systems to allow your current related files to be
picked up at any time. It is suggested that the actual filename indicate
the origin of the list to avoid confusion and overwriting. PGPFILES
requested from this system gets the requestor a file called: PGP37414.LST.
The contents of this Echo are archived on 1:374/14 as the area is purged.
The current past traffic is in the file PUBKEY.ECO. Archives are no longer
kept.
This Echo is currently available on the Zone 1 Backbone. It has been
EListed as of ELIST211. Please feel free to announce this Echo in all
Nets and Networks.
A companion Echo for the purpose of submitting public-keys only is now
available as PKEY_DROP Echo. PKEY_DROP may be obtained via the same channels
as PUBLIC_KEYS.
NOTE:
If you lose your secret-key password [or forget it] or your secret-key in a
drive crash [because you failed to back it up on floppy], you cannot issue a
revocation certificate. In that case, you should make a general announcement
in all related Echos that your old key should be disabled using the PGP
disable command [PGP -kd userid] for your userid. That keeps your useless
key on their keyrings [so they won't be replaced from other lists who didn't
get the word] and permits them to add a new key from you without one
interfering with the other. BACKUP! BACKUP! BACKUP! [clear?] [grin]
Thanks.
TTFN.
Christopher Baker & GK Pace
Moderators
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: SUPPORT the Phil Zimmerman Legal Defense Fund!
iQCVAwUBL6Ro3ssQPBL4miT5AQFS1wP+I+th/WPvzfT/JIuhmU2mVSHR26Im5Hd/
PG1J8d6eOCWv6hJc0uMPNQ1/AEEIrnLRMmsJFCOxo58IStu7L1idsWif3fceZbU8
ioaqLKJ6dsa7XaS0F5SKhyDCJxBMwb8ZK6AWE8S8pgkbWqum9XgDI2CbdG08caWK
1NyMZ+yq3bw=
=CxXe
-----END PGP SIGNATURE-----
--- GenMsg [0002] (cbak.rights@opus.global.org)
* Origin: Rights On! for Privacy! It's a Right not a privilege! (1:374/14)